Thanks for the PR.

tsd use it's own version of typescript.
We have no command or code directly link to use typescript either.
So, closing.

Thanks for the PR.

tsd use it's own version of typescript. We have no command or code directly link to use typescript either. So, closing.

ts-standard require eslint ts parser and have a peer deps of ts

warning " > ts-standard@12.0.2" has unmet peer dependency "typescript@*".
warning "ts-standard > eslint-config-standard-with-typescript@23.0.0" has unmet peer dependency "typescript@*".
warning "ts-standard > @typescript-eslint/eslint-plugin > tsutils@3.21.0" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".

it's not for tsd, it's for eslint

Absolutely a disaster when choosing to use ts-standard.
I would against it when I see it earlier.

ts-standard is leak of active contribution or maintenance.
It's dependencies is not updated since 2022 Dec.
See standard/ts-standard#286

Using it's underlying dependency directly provide more up-to-update experience.
And most of the dependency already changed to automatic publish. For example, eslint-config-standard-with-typescript.
See mightyiam/eslint-config-love@971c680

Not really against adding typescript, but the use of ts-standard.

Yes, another option

  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^5.59.2",
    "@typescript-eslint/parser": "^5.0.0",
    "benchmark": "^2.1.4",
    "eslint": "^8.40.0",
    "eslint-config-standard-with-typescript": "^34.0.1",
    "eslint-plugin-import": "^2.27.5",
    "eslint-plugin-n": "^15.0.0",
    "eslint-plugin-promise": "^6.0.0",
    "tap": "^16.0.0",
    "tsd": "^0.28.0",
    "typescript": "^5.0.4"
  },

I for the same reasons dislike this PR.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.